NH-3964 - obsolete Linq.ReflectionHelper in favor of Util.ReflectHelper. #586
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follow up of NH-3964 and its first PR #574 .
Methods are just moved to ReflectHelper, without changing them.
Trying to use
is requiring as many overloads as function arguments counts
Then type inference is sometime inferior:
Instead of
And handling instance methods are requiring a
Func<Func<>>
with a non-null instance:So well, even though some "brute force" runtime performance comparison show it is "better", I do not think it is worth all the required changes and additional code for using them.